Skip to content

feat: migrate agent to mpcp-gateway-client (phase 4b)#2

Open
naory wants to merge 1 commit intomainfrom
feat/mpcp-gateway-client-migration
Open

feat: migrate agent to mpcp-gateway-client (phase 4b)#2
naory wants to merge 1 commit intomainfrom
feat/mpcp-gateway-client-migration

Conversation

@naory
Copy link
Copy Markdown
Contributor

@naory naory commented Apr 4, 2026

Summary

Phase 4b migration: the Hyperbolic demo agent uses mpcp-gateway-client (GatewayClient.createSession with signedPolicyGrant, GatewaySession.fetch for inference) instead of @mpcp/agent + a separate EIP-712 signer service.

Env (breaking)

  • Required: MPCP_GATEWAY_URL, MPCP_GATEWAY_API_KEY
  • Optional: MPCP_SESSION_PURPOSE (default inference:llm), AGENT_ACTOR_ID, etc.
  • Removed from agent path: MPCP_SBA_SIGNING_KEY_PEM, SIGNER_URL

Also

Adds the full agent + Next web tree to git (these paths were previously untracked in this repo).

Test plan

  • npm run build (tsc)

Made with Cursor

- Replace @mpcp/agent Session + signer service with GatewayClient/GatewaySession
- Route Hyperbolic traffic through session.fetch (gateway proxy + x402)
- Config: MPCP_GATEWAY_URL, MPCP_GATEWAY_API_KEY; optional MPCP_SESSION_PURPOSE
- Remove signer-client; handle GatewayBudgetExceededError / GatewayGrantRevokedError
- tsconfig: ES2022 + DOM for Fetch types; extend .gitignore for web build artifacts
- Track full agent + web app sources (previously only docs/policy were in git)

Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant